@morpheus review — Approved ✅

Standard Android manifest merger workaround. tools:node="remove" on the permission and both plugin-provided receivers, targeting their fully qualified class names. tools namespace already declared. autoRunOnBoot/autoStartOnBoot both false in Dart — runtime no-op. Clean single commit with issue reference.

Greptile Summary

This PR fixes a Google Play Store rejection for targetSdk-35 builds by stripping two plugin-injected BOOT_COMPLETED receivers and the RECEIVE_BOOT_COMPLETED permission from the merged AndroidManifest.xml using tools:node="remove". The approach is the correct manifest-merger idiom and is safe given that autoRunOnBoot/autoStartOnBoot are already disabled in the Dart layer.

• Adds tools:node="remove" to the existing RECEIVE_BOOT_COMPLETED <uses-permission> declaration so neither the app nor any library manifest contributes the permission to the merged output.
• Inserts two stub <receiver> elements (targeting RebootReceiver from flutter_foreground_task and BootReceiver from flutter_background_service_android) with tools:node="remove" so the plugin manifests' receiver declarations are suppressed during the AGP merge step.

Confidence Score: 5/5

Safe to merge — the change is a targeted manifest-merger override that removes boot-autostart receivers that were never used at runtime.

The diff touches only three manifest declarations: it marks the unused RECEIVE_BOOT_COMPLETED permission and two plugin-injected boot receivers for removal via tools:node="remove". The app already disables both autoRunOnBoot and autoStartOnBoot in Dart, so removing the receivers has no effect on runtime behaviour. The PR author ran the manifest-merger tool locally and confirmed zero BOOT_COMPLETED occurrences in the merged output.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[AGP Manifest Merger] --> B{Process app AndroidManifest.xml}
    B --> C[RECEIVE_BOOT_COMPLETED\ntools:node=remove]
    B --> D[RebootReceiver stub\ntools:node=remove]
    B --> E[BootReceiver stub\ntools:node=remove]

    F[flutter_foreground_task manifest] --> G[RebootReceiver\nBOOT_COMPLETED intent-filter]
    H[flutter_background_service manifest] --> I[BootReceiver\nBOOT_COMPLETED intent-filter]
    J[App manifest] --> K[RECEIVE_BOOT_COMPLETED\npermission]

    G -->|merger conflict resolution| D
    I -->|merger conflict resolution| E
    K -->|merger conflict resolution| C

    C -->|removed| L[Merged AndroidManifest.xml]
    D -->|removed| L
    E -->|removed| L

    L --> M[0 BOOT_COMPLETED occurrences\n✓ Play Store accepted]

_{Reviews (2): Last reviewed commit: "android: strip BOOT_COMPLETED receivers ..." | Re-trigger Greptile}

Hey @mdmohsin7 👋

Thank you so much for taking the time to contribute to Omi! We truly appreciate you putting in the effort to submit this pull request.

After careful review, we've decided not to merge this particular PR. Please don't take this personally — we genuinely try to merge as many contributions as possible, but sometimes we have to make tough calls based on:

• Project standards — Ensuring consistency across the codebase
• User needs — Making sure changes align with what our users need
• Code best practices — Maintaining code quality and maintainability
• Project direction — Keeping aligned with our roadmap and vision

Your contribution is still valuable to us, and we'd love to see you contribute again in the future! If you'd like feedback on how to improve this PR or want to discuss alternative approaches, please don't hesitate to reach out.

Thank you for being part of the Omi community! 💜

#7159 closed the wrong pr